📄 openmetadata-ui/src/main/resources/ui/src/generated/type/changeEventType.ts:36 📄 openmetadata-spec/src/main/resources/json/schema/type/changeEventType.json:28
The JSON schema changeEventType.json defines "userLogin" and "userLogout", but all 8 generated TypeScript files contain UserLoggedIn = "userLoggedIn" and UserLoggedOut = "userLoggedOut". These string values don't match.

The TypeScript files appear to have been generated from a previous version of the schema (when the enum values were "userLoggedIn"/"userLoggedOut") and were not regenerated after the schema was updated in commit 21c3482 to use "userLogin"/"userLogout".

Impact: The backend Java code will serialize these event types as "userLogin"/"userLogout" (matching the schema), but the frontend TypeScript code will use "userLoggedIn"/"userLoggedOut". This means:

• Frontend event type filtering will fail to match backend events
• Any TypeScript code comparing against these enum values will never match actual API responses
• Type safety is broken across the full stack

Fix: Re-run the TypeScript code generator from the updated JSON schema so the TS enums produce UserLogin = "userLogin" and UserLogout = "userLogout".

📄 openmetadata-spec/src/main/resources/json/schema/type/changeEventType.json:28 📄 openmetadata-service/src/main/java/org/openmetadata/service/audit/AuditLogRepository.java:503
The old string constants used "userLogin" / "userLogout", but the new enum values serialize to "userLoggedIn" / "userLoggedOut". This introduces two problems:

1. Backward compatibility for existing data: Any audit log records already stored in the database with event_type = "userLogin" or "userLogout" will no longer match the new values. The formatAuthEventSummary() method (line 503) now compares against "userLoggedIn", so old records will fall through to the raw return eventType instead of getting the human-readable summary.

2. Integration tests are broken: The tests in AuditLogResourceIT.java still reference the old event type strings ("userLogin", "userLogout") and will fail, as the new code stores different values.

Suggested fix options:

• Option A: Add a data migration to update existing event_type values from "userLogin" → "userLoggedIn" and "userLogout" → "userLoggedOut" in the audit log table, and update the integration tests.
• Option B: In formatAuthEventSummary(), also check for the legacy string values alongside the new enum values, and update the integration tests.
• Option C: Change the enum values in the JSON schema to match the old strings ("userLogin", "userLogout") to maintain backward compatibility without migration.